Repository navigation
feat(docker/build-push): add target and build-args inputs - #259
Merged
Merged
Conversation
Lets a caller build one stage of a multi-stage Dockerfile, and variants of it, without a Dockerfile per variant.
chjdev
enabled auto-merge (rebase)
November 17, 2026 10:14
antholzer
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds two optional inputs to
docker/build-push, passed unchanged todocker/build-push-action:target: the Dockerfile stage to build. Empty builds the last stage.build-args: oneKEY=VALUEper line.devclaude needs both to publish the
basestage of its Dockerfile, once plain and once withDEVCLAUDE_DIND=1. The final stage needs per-user build args, so building it in CI isn't an option.Both default to empty, which
docker/build-push-actiontreats as unset, so existing callers behave as before.